Allow using route bindings on frontend #71
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Released as part of v1.0.0-alpha.11. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Frontend routes
Statamic (and by extension, Cargo) only registers route bindings on non-CP routes to avoid potential conflicts with existing apps.
If you know there aren't going to be any conflicts, you may override the behaviour in the
routes.phpconfig file:This pull request ensures that Cargo takes the
bindingsconfig option into account when registering route bindings, mirroring Statamic.Unable to use
{order}in frontend routeThis pull request also fixes an issue when trying to use
{order}in a frontend route, where Cargo would returnfalseinstead of returning the value from the URL.Fixes #70